Prevent generic phrases from becoming direct beneficiaries

When a denylisted alias appears after a direct-beneficiary cue, this branch runs before the generic-alias check below, so text such as funding for cybersecurity is emitted as direct_beneficiary for PANW/CRWD rather than industry_context. That turns sector-level funding language into company-level evidence and can corrupt the relationship fields the commit is adding; the direct pattern should not promote aliases that are only generic context terms.

Useful? React with 👍 / 👎.

Normalize configured generic alias variants

This exact membership check misses generic aliases already present in config/core_us_equity_aliases.csv, for example energy related infrastructure alongside the denylisted hyphenated form on config lines 9, 24, 40, and 41. A government-policy item containing the unhyphenated phrase therefore falls through to issuer evidence instead of industry_context; normalize equivalent hyphen/space variants or include the configured variants in the generic classification.

Useful? React with 👍 / 👎.

Deduplicate repeated symbols after evidence matching

When an operator-provided aliases CSV has more than one row for the same symbol, this per-alias-record loop appends one event for each row; unlike the previous match_symbols path, nothing deduplicates by symbol before writing. That produces duplicate event_id rows for one source item, which downstream tracker/event-study code counts as separate events and can inflate scores or returns unless the strongest evidence is collapsed per (item_id, symbol).

Useful? React with 👍 / 👎.

Anchor direct-beneficiary aliases at word boundaries

Because this direct-beneficiary regex inserts the escaped alias without the same trailing boundary used by alias_pattern, an item that mentions a company elsewhere can be upgraded by a prefix match in an unrelated beneficiary, e.g. Ford earnings were discussed. Funding for Fordham University... returns direct_beneficiary for Ford. Reusing the alias boundary here avoids turning longer names that merely start with a ticker/company alias into direct company evidence.

Useful? React with 👍 / 👎.

Prefer explicit aliases over generic context

When one item contains both a real company alias and a denylisted context alias for the same symbol, this ordering causes the generic match to win because industry_context outranks unverified; for example, PANW aliases include both Palo Alto Networks and cybersecurity, so a government item like Palo Alto Networks cybersecurity guidance is emitted as industry_context with match_evidence=cybersecurity. That loses the explicit company-name evidence in the new relationship fields, so generic aliases should only win when no non-generic company/ticker alias matched.

Useful? React with 👍 / 👎.

Remove reversed benefits-from cue

When a sentence says another party benefits from a company, this cue treats the company after benefits from as the direct beneficiary. For example, a government item like Domestic suppliers benefit from Intel investment marks INTC as direct_beneficiary, even though the beneficiaries are the suppliers and Intel is just source/context, which overstates company-level support in the new relationship fields.

Useful? React with 👍 / 👎.

Do not trust third-party names in issuer releases

When any issuer_release item mentions another covered company by its canonical name, this branch promotes that other company to issuer evidence even though source_items.csv has no field identifying which issuer owns the release. For example, an NVIDIA issuer release saying it partnered with Palo Alto Networks would emit PANW as issuer evidence instead of a third-party mention; only promote issuer evidence when the release can be tied to the same symbol.

Useful? React with 👍 / 👎.